[pull] main from sparklemotion:main #3

pull · 2021-10-22T18:24:46Z

See Commits and Changes for more details.

Can you help keep this open source service alive? 💖 Please sponsor : )

google-cla · 2021-10-22T18:25:21Z

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

What to do if you already signed the CLA

Individual signers

It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

google-cla · 2021-10-23T18:01:27Z

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

What to do if you already signed the CLA

Individual signers

It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

google-cla · 2021-10-23T18:02:11Z

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

What to do if you already signed the CLA

Individual signers

It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

google-cla · 2021-10-23T20:12:28Z

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

What to do if you already signed the CLA

Individual signers

It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

google-cla · 2021-10-26T17:19:36Z

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

What to do if you already signed the CLA

Individual signers

It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

google-cla · 2021-10-27T19:08:01Z

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

What to do if you already signed the CLA

Individual signers

It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

google-cla · 2021-10-28T15:02:45Z

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

What to do if you already signed the CLA

Individual signers

It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

google-cla · 2021-11-03T17:33:15Z

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

What to do if you already signed the CLA

Individual signers

It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

google-cla · 2021-11-03T17:34:30Z

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

What to do if you already signed the CLA

Individual signers

It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

google-cla · 2021-11-06T16:47:05Z

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

What to do if you already signed the CLA

Individual signers

It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

google-cla · 2021-11-06T16:47:29Z

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

What to do if you already signed the CLA

Individual signers

It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

google-cla · 2021-11-12T21:11:27Z

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

What to do if you already signed the CLA

Individual signers

It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

google-cla · 2021-11-15T14:05:37Z

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

What to do if you already signed the CLA

Individual signers

It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

google-cla · 2021-11-15T14:06:26Z

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

What to do if you already signed the CLA

Individual signers

It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

google-cla · 2021-11-15T18:56:52Z

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

What to do if you already signed the CLA

Individual signers

It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

google-cla · 2021-11-15T18:58:12Z

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

What to do if you already signed the CLA

Individual signers

It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

Trying to address concerns raised in #1053. [skip ci]

Closes #1523

…3268) **What problem is this PR intended to solve?** Closes #1523 **Have you included adequate test coverage?** Yes. **Does this change affect the behavior of either the C or the Java implementations?** This makes the Java impl behave like the C impl.

The behavior is different between Java and C impls in a way that I don't care enough to fix. Let's document the difference and move on with our lives.

…3269) **What problem is this PR intended to solve?** The behavior is different between Java and C impls in a way that I don't care enough to fix. Let's document the difference and move on with our lives. Closes #1758 **Have you included adequate test coverage?** Yes. **Does this change affect the behavior of either the C or the Java implementations?** N/A

Let's just work around it in the tests. The behavior we're testing isn't specific to UTF-8, so let's just swap in ISO-2022-JP. GNOME/libxml2@6d8427dc

@nwellnhof

…3271) **What problem is this PR intended to solve?** Example failure: https://github.com/sparklemotion/nokogiri/actions/runs/9774049613/job/26981486984 Let's just work around it in the tests. The behavior we're testing isn't specific to UTF-8, so let's just swap in ISO-2022-JP. GNOME/libxml2@6d8427dc Tagging @nwellnhof just for awareness. **Have you included adequate test coverage?** Yes **Does this change affect the behavior of either the C or the Java implementations?** N/A

Two things getting fixed here: 1. We were not calling `setFeature(FEATURE_NOT_EXPAND_ENTITY, ...)` correctly. It defaults to true, and we were conditionally setting it to true. Instead, let's just explicitly set this feature (and the other features we care about) to avoid mistaken assumptions about the default. 2. We were rendering the children of the EntityReference, which contains the replacement text, as well as the EntityReference itself. We should only ever render one or the other. If NOENT is false, though, there won't be any EntityReferences in the DOM. So: if we encounter an EntityReference, don't render its children. See https://xerces.apache.org/xerces-j/features.html section on `create-entity-ref-nodes` for a deeper explanation of the parser behavior. Closes #3270

…3272) **What problem is this PR intended to solve?** Two things getting fixed here: 1. We were not calling `setFeature(FEATURE_NOT_EXPAND_ENTITY, ...)` correctly. It defaults to true, and we were conditionally setting it to true. Instead, let's just explicitly set this feature (and the other features we care about) to avoid mistaken assumptions about the default. 2. We were rendering the children of the EntityReference, which contains the replacement text, as well as the EntityReference itself. We should only ever render one or the other. If NOENT is false, though, there won't be any EntityReferences in the DOM. So: if we encounter an EntityReference, don't render its children. See https://xerces.apache.org/xerces-j/features.html section on `create-entity-ref-nodes` for a deeper explanation of the parser behavior. Closes #3270 **Have you included adequate test coverage?** Yes **Does this change affect the behavior of either the C or the Java implementations?** This fixes a bug in the Java implementation, so it behaves like the C impl.

See ruby/ruby#11085 for discussion

See: - https://gitlab.gnome.org/GNOME/libxml2/-/issues/758 - https://gitlab.gnome.org/GNOME/libxml2/-/merge_requests/271 [skip ci]

**What problem is this PR intended to solve?** Build a container for libxml2 to use in its pipeline See: - https://gitlab.gnome.org/GNOME/libxml2/-/issues/758 - https://gitlab.gnome.org/GNOME/libxml2/-/merge_requests/271

unless the test specifies one or the other. Closes #3242

Updates the requirements on [ruby_memcheck](https://github.com/Shopify/ruby_memcheck) to permit the latest version. - [Release notes](https://github.com/Shopify/ruby_memcheck/releases) - [Commits](Shopify/ruby_memcheck@3.0.0...3.0.1) --- updated-dependencies: - dependency-name: ruby_memcheck dependency-type: direct:development ... Signed-off-by: dependabot[bot] <[email protected]>

- drop adding the flat namespace linker flag which rcd injects for us - detect the need for darwin linker hack based on linker flags, not ruby version

**What problem is this PR intended to solve?** Bump rake-compiler-dock to 1.8.0, see https://github.com/rake-compiler/rake-compiler-dock/releases/tag/v1.8.0

Updates the requirements on [rake-compiler](https://github.com/luislavena/rake-compiler) to permit the latest version. - [Release notes](https://github.com/luislavena/rake-compiler/releases) - [Changelog](https://github.com/rake-compiler/rake-compiler/blob/master/History.md) - [Commits](rake-compiler/rake-compiler@v1.2.8...v1.2.9) --- updated-dependencies: - dependency-name: rake-compiler dependency-type: direct:development ... Signed-off-by: dependabot[bot] <[email protected]>

[skip ci]

…#3408)

…#3407)

Updates the requirements on [rubyzip](https://github.com/rubyzip/rubyzip) to permit the latest version. - [Release notes](https://github.com/rubyzip/rubyzip/releases) - [Changelog](https://github.com/rubyzip/rubyzip/blob/master/Changelog.md) - [Commits](rubyzip/rubyzip@v2.3.2...v2.4.1) --- updated-dependencies: - dependency-name: rubyzip dependency-type: direct:development ... Signed-off-by: dependabot[bot] <[email protected]>

…#3406)

**What problem is this PR intended to solve?** Recently we've been getting upstream CI failures for libxml2 head on ubuntu: https://github.com/sparklemotion/nokogiri/actions/runs/12705536326/job/35416744559 ``` configure:15841: checking for liblzma configure:15848: $PKG_CONFIG --exists --print-errors "liblzma" Package liblzma was not found in the pkg-config search path. Perhaps you should add the directory containing `liblzma.pc' to the PKG_CONFIG_PATH environment variable Package 'liblzma', required by 'virtual:world', not found configure:15851: $? = 1 configure:15865: $PKG_CONFIG --exists --print-errors "liblzma" *** ../../../../ext/nokogiri/extconf.rb failed *** ```

to reflect modern bundler usage

should have been removed in f6eede5

When performing a CSS selector query, an XML document's root namespace declarations are injected into the XPathVisitor, and the default namespace is applied to any non-namespaced element in the resulting xpath query. However, the wildcard selector "*" should not have this namespace applied. This regressed in v1.17.0 with 179d74d. Fixes #3411

this time, it's the ruby:alpine images that removed all the -dev libraries. JFC i'm just trying to stay green here.

…3413) **What problem is this PR intended to solve?** When performing a CSS selector query, an XML document's root namespace declarations are injected into the XPathVisitor, and the default namespace is applied to any non-namespaced element in the resulting xpath query. However, the wildcard selector "*" should not have this namespace applied. This regressed in v1.17.0 with 179d74d. Fixes #3411 **Have you included adequate test coverage?** Yes. **Does this change affect the behavior of either the C or the Java implementations?** N/A

**What problem is this PR intended to solve?** Adds a doc about "modernized" call-seqs. A modernized method's doc can link to this doc. This should allow a simpler discussion in the method's doc. **Have you included adequate test coverage?** Doc only. **Does this change affect the behavior of either the C or the Java implementations?** No.

ref: #3362

Updates the requirements on [standard](https://github.com/standardrb/standard) to permit the latest version. - [Release notes](https://github.com/standardrb/standard/releases) - [Changelog](https://github.com/standardrb/standard/blob/main/CHANGELOG.md) - [Commits](standardrb/standard@v1.43.0...v1.44.0) --- updated-dependencies: - dependency-name: standard dependency-type: direct:development ... Signed-off-by: dependabot[bot] <[email protected]>

Updates the requirements on [rdoc](https://github.com/ruby/rdoc) to permit the latest version. - [Release notes](https://github.com/ruby/rdoc/releases) - [Changelog](https://github.com/ruby/rdoc/blob/master/History.rdoc) - [Commits](ruby/rdoc@v6.10.0...v6.11.0) --- updated-dependencies: - dependency-name: rdoc dependency-type: direct:development ... Signed-off-by: dependabot[bot] <[email protected]>

…3416)

and replace the .cross_rubies file with misc/native.yml

**What problem is this PR intended to solve?** Update to rake-compiler-dock v1.9.1 and replace the .cross_rubies file with misc/native.yml

[skip ci]

**What problem is this PR intended to solve?** Improvements to doc for XML::ParseOptions. **Have you included adequate test coverage?** N/A. All doc. **Does this change affect the behavior of either the C or the Java implementations?** No. --------- Co-authored-by: Mike Dalessio <[email protected]>

pull bot added the ⤵️ pull label Oct 22, 2021

flavorjones added 13 commits July 2, 2024 14:49

doc: improve documentation for Node#content= and #native_content=

47626c8

Trying to address concerns raised in #1053. [skip ci]

fix(jruby): Reader#outer_xml and #inner_xml encode entities properly

9213c48

Closes #1523

test: add test coverage describing how pushparser handles empty docs

c208799

The behavior is different between Java and C impls in a way that I don't care enough to fix. Let's document the difference and move on with our lives.

fix: upstream libxml2 is now returning null for UTF-8 enc handler

2795d91

Let's just work around it in the tests. The behavior we're testing isn't specific to UTF-8, so let's just swap in ISO-2022-JP. GNOME/libxml2@6d8427dc

ext: don't split the compiler flags when appending env vars

4b4307f

See ruby/ruby#11085 for discussion

ci: build a container for libxml2 to use in its pipeline

cfbf9bb

See: - https://gitlab.gnome.org/GNOME/libxml2/-/issues/758 - https://gitlab.gnome.org/GNOME/libxml2/-/merge_requests/271 [skip ci]

ci: build a container for libxml2 to use in its pipeline (#3275)

0120972

**What problem is this PR intended to solve?** Build a container for libxml2 to use in its pipeline See: - https://gitlab.gnome.org/GNOME/libxml2/-/issues/758 - https://gitlab.gnome.org/GNOME/libxml2/-/merge_requests/271

test: run html5lib-tests in both script-on and script-off modes

cadb1f8

unless the test specifies one or the other. Closes #3242

flavorjones and others added 30 commits January 5, 2025 21:42

dep: bump rake-compiler-dock to 1.8.0

d5f2a83

ext: update for rake-compiler-dock 1.8.0

dbfd8f8

- drop adding the flat namespace linker flag which rcd injects for us - detect the need for darwin linker hack based on linker flags, not ruby version

dep: bump rake-compiler-dock to 1.8.0 (#3404)

b2a7890

**What problem is this PR intended to solve?** Bump rake-compiler-dock to 1.8.0, see https://github.com/rake-compiler/rake-compiler-dock/releases/tag/v1.8.0

doc: update CHANGELOG with rake-compiler-dock updates

8c76912

[skip ci]

build(deps-dev): update rake-compiler requirement from 1.2.8 to 1.2.9 (…

4d617fa

…#3408)

build(deps-dev): update ruby_memcheck requirement from 3.0.0 to 3.0.1 (…

2e037aa

…#3407)

test: drop unnecessary assertion on rubyzip read encoding

af5b1b0

build(deps-dev): update rubyzip requirement from ~> 2.3.2 to ~> 2.4.1 (…

c5cd95a

…#3406)

ci: make sure liblzma is installed

adc292e

doc: update the glibc error comment

e375018

to reflect modern bundler usage

doc: remove comment about jruby xpath searches

b63f0a8

should have been removed in f6eede5

prefactor: restructure css-to-xpath tests

b7fc73c

dev: so tired of psych not building on various things

671462f

this time, it's the ruby:alpine images that removed all the -dev libraries. JFC i'm just trying to stay green here.

doc: add the doc/ subdirectory to the rdoc files

62e7180

ref: #3362

dev: better protection against rdoc/psych not being loaded

acac18d

build(deps-dev): update rdoc requirement from 6.10.0 to 6.11.0 (#3417)

5fcd6c3

build(deps-dev): update standard requirement from 1.43.0 to 1.44.0 (#…

53ecfd4

…3416)

dep: update to rake-compiler-dock v1.9.1

0994b4e

and replace the .cross_rubies file with misc/native.yml

dep: update to rake-compiler-dock v1.9.1 (#3418)

b2bf25d

**What problem is this PR intended to solve?** Update to rake-compiler-dock v1.9.1 and replace the .cross_rubies file with misc/native.yml

doc: update CHANGELOG

6830270

[skip ci]

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[pull] main from sparklemotion:main #3

[pull] main from sparklemotion:main #3

pull bot commented Oct 22, 2021 •

edited

Loading

google-cla bot commented Oct 22, 2021

google-cla bot commented Oct 23, 2021

google-cla bot commented Oct 23, 2021

google-cla bot commented Oct 23, 2021

google-cla bot commented Oct 26, 2021

google-cla bot commented Oct 27, 2021

google-cla bot commented Oct 28, 2021

google-cla bot commented Nov 3, 2021

google-cla bot commented Nov 3, 2021

google-cla bot commented Nov 6, 2021

google-cla bot commented Nov 6, 2021

google-cla bot commented Nov 12, 2021

google-cla bot commented Nov 15, 2021

google-cla bot commented Nov 15, 2021

google-cla bot commented Nov 15, 2021

google-cla bot commented Nov 15, 2021

[pull] main from sparklemotion:main #3

Are you sure you want to change the base?

[pull] main from sparklemotion:main #3

Conversation

pull bot commented Oct 22, 2021 • edited Loading

google-cla bot commented Oct 22, 2021

What to do if you already signed the CLA

Individual signers

Corporate signers

google-cla bot commented Oct 23, 2021

What to do if you already signed the CLA

Individual signers

Corporate signers

google-cla bot commented Oct 23, 2021

What to do if you already signed the CLA

Individual signers

Corporate signers

google-cla bot commented Oct 23, 2021

What to do if you already signed the CLA

Individual signers

Corporate signers

google-cla bot commented Oct 26, 2021

What to do if you already signed the CLA

Individual signers

Corporate signers

google-cla bot commented Oct 27, 2021

What to do if you already signed the CLA

Individual signers

Corporate signers

google-cla bot commented Oct 28, 2021

What to do if you already signed the CLA

Individual signers

Corporate signers

google-cla bot commented Nov 3, 2021

What to do if you already signed the CLA

Individual signers

Corporate signers

google-cla bot commented Nov 3, 2021

What to do if you already signed the CLA

Individual signers

Corporate signers

google-cla bot commented Nov 6, 2021

What to do if you already signed the CLA

Individual signers

Corporate signers

google-cla bot commented Nov 6, 2021

What to do if you already signed the CLA

Individual signers

Corporate signers

google-cla bot commented Nov 12, 2021

What to do if you already signed the CLA

Individual signers

Corporate signers

google-cla bot commented Nov 15, 2021

What to do if you already signed the CLA

Individual signers

Corporate signers

google-cla bot commented Nov 15, 2021

What to do if you already signed the CLA

Individual signers

Corporate signers

google-cla bot commented Nov 15, 2021

What to do if you already signed the CLA

Individual signers

Corporate signers

google-cla bot commented Nov 15, 2021

What to do if you already signed the CLA

Individual signers

Corporate signers

pull bot commented Oct 22, 2021 •

edited

Loading